[DOCS] all tabs: finish the 0.7 sweep for versions, ACPs, and encrypted types - #58

The card was titled Cofhejs and linked to the legacy tab, while the
comment above it read {/* @SDK */}. cofhejs is superseded by @cofhe/sdk,
so the landing page was sending readers to the wrong library.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Both pages described the 0.6 shape: a signed EncryptedItemInput per value
and permits managed through client.permits.

They now describe one batch (a handle per input plus a shared signature,
with the consuming contract declared before signing) and ACPs through
client.acp. The sequence diagram carries the same correction, since it
showed CoFHE returning a signed EncryptedItemInput.

The @cofhe/sdk/permits entrypoint is now @cofhe/sdk/acps. Checked against
the 0.7.1 package exports, where ./permits no longer resolves.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Every remaining client-sdk page, checked one at a time against the 0.7.1
packages rather than swept with a pattern.

Prose and the SDK API move to ACP: client.acp, withACP/withoutACP,
ACPUtils, and the @cofhe/sdk/acps entrypoint, which is what the package
actually exports now (./permits no longer resolves).

The Foundry plugin renamed its Solidity API too, which a JS-only rename
would have missed: createInEuintN became createExternalEuintN and now
takes the consuming contract and returns a (handle, proof) pair;
permit_createSelf became ACP_createSelf; decryptForTx_withoutPermit
became decryptForTx_withoutACP; the Permission struct is now ACP,
imported from the same Permissioned.sol.

Examples move to the batch shape: setConsumingContract before execute,
and a destructure that accounts for the trailing signature.

Deliberately left alone: the old-API column of the mock-contracts 0.4
mapping table, the cofhejs column of the cofhejs guide, the Before
blocks in the 0.7 guide, and the sentences that name a removed symbol in
order to explain that it was removed.

Also corrects the localcofhe chain id, which the pre-configured networks
table left blank, and drops assertCorrectEncryptedItemInput from the
entrypoint list since it resolves to zero files in 0.7.1.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

InEuintXX is deleted in cofhe-contracts 0.2.0. Every affected function
signature now takes externalEuintXX plus the bytes proof that
authenticates it, and each FHE.asEuintXX call passes both.

Adds the type family that was missing entirely: sharedEuintXX, for values
handed from one contract to another. inputs.mdx gains a section on it,
covering the Param and FromCall receive forms and why the type exists,
which is that FHE operations check the permission of the contract doing
them rather than the caller, so a bare euintXX parameter is a disclosure
path. encrypted-operations and the FHE.sol reference now list all three
families side by side.

The multi-input examples use the plural asEuintXXs form. Two inputs share
one batch signature, so converting them one at a time verifies each hash
against a signature covering both and reverts. Signatures checked against
FHE.sol 0.2.0 rather than inferred.

confidential-contracts is untouched and stays for its own branch.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

…ermits to ACPs

The component table said the FheOS Server executes the FHE computations
and left the FHE Engine out of the table entirely. STYLE.md is explicit
that FheOS verifies and queues incoming work and does not execute FHE
operations, and that the FHE Engine is what executes them. Both rows are
now correct.

Also renames permits to ACPs across the page, including the flow diagram
and the link to the ACP guide.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>